The hardware and software of your WriteMove have been thoroughly tested during their development. These release notes provide you with a summary of the results of our testing effort, up-to-date information on software compatibility, and some general information on ways to improve your printing productivity.
Before installing the software, you must first read the installation instructions provided in the WriteMove User’s Manual.
If you do not have the WriteMove User’s Manual or if you are missing any of the disks or other manuals, please contact your dealer or call GCC Technologies™ Customer Support at (800) 422-7777 to obtain these documents.
• 7.0 Compatibility
WriteMove 2.0.2 is fully compatible with system 7.0, allowing you to use 32-bit addressing and Virtual Memory (VM) while printing, assuming your application is itself “32-bit clean” and compatible with VM.
VM makes it appear as though your machine has more memory available than the actual amount of physical memory (RAM) installed, so you may be able to print documents which were too large or complex to print when only the RAM on your machine was available.
Because accessing a hard disk is slower than accessing RAM, use of VM typically increases the time required to print a document with the WriteMove. If several applications are running simultaneously, available RAM will be reduced and the WriteMove software may have to access the disk more frequently, thus reducing printing speed. However, it is possible that, if enough of the data not required by WriteMove is moved out to the disk, more RAM will be available to the WriteMove software than would have been the case without VM. In this case, the time required to print may actually decrease.
If you find that VM causes unacceptable increases in printing time and you are running multiple applications simultaneously, try closing the other applications before printing. If this does not help, you may want to turn VM off.
QuickSpool II has been tested with System 7.0 and found to be incompatible. GCC does not recommend using QuickSpool II with System 7.0; the Installer will not install QuickSpool II if you are running System 7.0. System 6.0.x users can use QuickSpool II with confidence, it has been thoroughly tested and qualified for use with System 6.0. See the QuickSpool II Release notes below for more information.
• TrueType Compatibility
WriteMove 2.0.2 will print using TrueType fonts (including rotated and flipped text) if your screen font is a TrueType font and there is no corresponding GCC font in your Font File Folder.
• 3rd Party Font Substitution
If you have replaced GCC fonts with either ATM® or TrueType® you can now use the font substitution features of the WriteMove software. Font Substitution will now take place if outline fonts (ATM or TrueType) are installed for Helvetica, Times, or Courier. Please note, however, that there may be line-layout problems when fonts are substituted since the character widths are vastly different between New York and Times, Geneva and Helvetica, and Monaco and Courier. If you have installed TrueType Geneva, Monaco and New York, you can avoid these problems by printing without Font Substitution.
• Font Installation
Beginning with System 6.0, Apple's Installer installed bitmapped fonts for Times, Helvetica, Courier, and Symbol. GCC includes Times, Helvetica, Courier and Symbol bitmaps with our printers as well, but the are different. Because GCC fonts originate from Bitstream, and Apple uses Adobe fonts in the LaserWriters, the character widths may vary slightly. In order to ensure that the correct widths are being used, you should first remove Times, Helvetica, Courier, and Symbol before installing GCC’s fonts. Installing GCC’s fonts over Apple’s may cause some line layout problems in printed documents.
• Temporary Memory
When running under MultiFinder or System 7.0, WriteMove 2.0.2 may use memory outside the application’s memory partition, if there is any available. This extra memory is called Temporary Memory.
When you choose ‘Print Now’ from the Print dialog, WriteMove 2.0.2 will make use of Temporary Memory. In many cases, documents which could not be printed from the application because of a lack of memory can now be printed because of WriteMove's use of Temporary Memory. You may no longer need to increase the ‘Application Memory Size’ value in the Get Info dialog of your application in order to print, since Temporary Memory is usually available. In fact, if an “Out of Memory” error occurs when printing with WriteMove 2.0.2, you may find that by reducing the ‘Application Memory Size’ value to the ‘Suggested Memory Size’ you will be able to print, because by reducing the application’s memory partiction, you are making more Temporary Memory available.
• System Memory
Because WriteMove 2.0.2 resides in the System’s memory partition rather than in the application’s memory partition, you may find that documents which could not be printed from the application due to lack of memory can now be printed. Because WriteMove 2.0.2 is not using the application’s memory, more memory is available for printing from within the application.
• WriteMove 2.0.1 Changes
Fixes an incompatibility with Microsoft Mail 3.0 which caused Microsoft Mail to crash whenever it tried to print.
Corrects some spacing problems when using Adobe Type Manager.
Corrects some "Out of Memory" message when printing multiple documents from the GCC Print Manager application.
• WriteMove 2.0.2 Changes
Fixes -39 error which could occur during spooling the print file to disk.
QuickSpool II v 1.02 Release Notes
-------------------------------
Your WriteMove and the accompanying software are designed to provide a total printing solution, without the addition of external software. We recommend that you use only the QuickSpool II spooling software that is provided with the WriteMove. For best results, remember to use the Tractor-Feed Paper Source option in the Print dialog box with QuickSpool II.
If you are using QuickSpool II with an ImageWriter, you may need to restart your Macintosh if you turn QuickSpool II Off and then back On. If QuickSpool II does not resume spooling when turned back On, simply restart your Macintosh.
If you switch printers on a port while QuickSpool II is turned On, then you will need to either restart your Macintosh, or turn QuickSpool II Off and then back On to ensure that your spooler operates properly.
If you experience problems with the “Retro.SCSI” INIT (which is included with the Retrospect™ archiving software), and QuickSpool II at startup time, rename the “Retro.SCSI” file by adding a character in front of its name. This will force the INIT to install at a different time when turning on your Macintosh. Due to the presence of other INITs on your machine, you may need to experiment with the character you add in front of the INIT’s name in order to get “Retro.SCSI” and QuickSpool II to install successfully.
If you use the “Print Stack” command in HyperCard®, your document will print without spooling. QuickSpool II has no effect in this particular situation.
QuickSpool II’s performance is very dependent upon the length of the documents you are printing. In fact, it is even possible for a short 1-page document to take longer to print when QuickSpool II is turned On, than if the document was printed without QuickSpool II. This is because the time spent to save the print job to disk is larger than the savings in time from printing in background. In these special cases, it may be worthwhile to turn QuickSpool II Off to print the document, and then turn it back On.
QuickSpool II is not with compatible System 7.0. It fails to print correctly under various circumstances, causes system errors, and has problems displaying dialogs. GCC does not recommend using QuickSpool II with System 7.0; the Installer will not install QuickSpool II if you are running System 7.0. None of these problems affect System 6.0.x users, QuickSpool II continues to perform reliably and well under System 6.0.x.